<?xml version="1.0"?>
<rss version="2.0">
  <channel><title>Problems</title><link>http://bill.welliver.org//space/pike/Objective C Bridge/Problems</link><description>&lt;i class="ital"&gt;A list of current engineering issues related to development of the Objective-C bridge. Intended primarily as a reminder of things left unfinished at the end of a long day. Comments are always welcome!&lt;/i&gt;&lt;p class="paragraph"/&gt;
&lt;b class="bold"&gt;problem:&lt;/b&gt; when the objective-c runtime calls a function from a pike object inherited from an objective-c class, the objective-c implementation of the function does not receive the pike scope of the object. as a result, if that objective-c implemented function (init, for example) returns itself, it returns the embedded native objective-c object rather than the "full" (pike + objective-c) object.&lt;p class="paragraph"/&gt;
&lt;b class="bold"&gt;proposed workaround:&lt;/b&gt; check to see if the returned objective-c level object is the same as the object returned. if it is, then the method returned itself and we can simply return the original pike object.&lt;p class="paragraph"/&gt;
&lt;b class="bold"&gt;discussion:&lt;/b&gt; are there side effects to this method? does it always work?</description><generator>Fins 0.9.7</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs></channel>
</rss>
